Micron Document
<!DOCTYPE html>
<html class="client-nojs vector-feature-night-mode-disabled vector-feature-language-in-header-enabled vector-feature-language-in-main-page-header-disabled vector-feature-page-tools-pinned-disabled vector-feature-toc-pinned-clientpref-1 vector-feature-main-menu-pinned-disabled vector-feature-limited-width-clientpref-1 vector-feature-limited-width-content-enabled vector-feature-custom-font-size-clientpref-1 vector-feature-appearance-pinned-clientpref-1 vector-sticky-header-enabled" lang="en" dir="ltr"><head>
<meta charset="UTF-8">
<title>Operational acceptance testing</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link rel="canonical" href="https://en.wikipedia.org/wiki/Operational_acceptance_testing"> <link href="./mw/ext.cite.styles.css" rel="stylesheet" type="text/css">
<link href="./mw/skins.vector.icons.css" rel="stylesheet" type="text/css">
<link href="./mw/skins.vector.search.codex.styles.css" rel="stylesheet" type="text/css">
<link href="./mw/skins.vector.styles.css" rel="stylesheet" type="text/css">
<link href="./mw/user.styles.css" rel="stylesheet" type="text/css">
<meta name="ResourceLoaderDynamicStyles" content="">
<link rel="stylesheet" type="text/css" href="./mw/site.styles.css">
<link rel="stylesheet" type="text/css" href="./mw/noscript.css">
<link rel="stylesheet" type="text/css" href="./footer.css">
<link rel="stylesheet" type="text/css" href="./vector-2022.css">
</head>
<body class="skin--responsive skin-vector skin-vector-search-vue mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject page-Operational_acceptance_testing rootpage-Operational_acceptance_testing skin-vector-2022 action-view">
<div class="mw-page-container">
<div class="mw-page-container-inner">
<div class="mw-content-container">
<main id="content" class="mw-body">
<header class="mw-body-header vector-page-titlebar">
<h1 id="firstHeading" class="firstHeading mw-first-heading">
<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Operational acceptance testing</span></span>
</h1>
</header>
<a id="top"></a>
<div id="bodyContent" class="vector-body ve-init-mw-desktopArticleTarget-targetContainer" aria-labelledby="firstHeading" data-mw-ve-target-container="">
<div id="mw-content-text" class="mw-body-content mw-content-ltr" lang="en" dir="ltr"><div class="mw-content-ltr mw-parser-output" lang="en" dir="ltr">
<p><b>Operational acceptance testing</b> (<b>OAT</b>) is used to conduct operational readiness (pre-release) of a product, service, or system as part of a <a href="Quality_management_system" title="Quality management system">quality management system</a>. OAT is a common type of non-functional <a href="Software_testing" title="Software testing">software testing</a>, used mainly in <a href="Software_development" title="Software development">software development</a> and <a href="Software_maintenance" title="Software maintenance">software maintenance</a> projects. This type of testing focuses on the operational readiness of the system to be supported, and/or to become part of the production environment. Hence, it is also known as <b>operational readiness testing</b> (<b>ORT</b>) or <b>operations readiness and assurance testing</b> (<b>OR&amp;A</b>). <a href="Functional_testing" title="Functional testing">Functional testing</a> within OAT is limited to those tests which are required to verify the <i>non-functional</i> aspects of the system.
</p><p>OAT elaborates upon and compartmentalises operational aspects of acceptance testing.<sup id="cite_ref-1" class="reference"><a href="#cite_note-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup>
</p><p>According to the International Software Testing Qualifications Board (ISTQB), OAT may include checking the <a href="Backup" title="Backup">backup</a>/restore facilities, IT <a href="IT_disaster_recovery" title="IT disaster recovery">disaster recovery</a> procedures, maintenance tasks and periodic check of security vulnerabilities.,<sup id="cite_ref-2" class="reference"><a href="#cite_note-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup> and whitepapers on ISO 29119 and Operational Acceptance by Anthony Woods,<sup id="cite_ref-ISO_29119_OAT_3-0" class="reference"><a href="#cite_note-ISO_29119_OAT-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup> and ISO 25000 and Operational Acceptance Testing by Dirk Dach et al., OAT generally includes:<sup id="cite_ref-4" class="reference"><a href="#cite_note-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup>
</p>
<ul><li>Component Testing</li>
<li>Failover (Within the same data centre)</li></ul>
<dl><dd><ul><li>Component fail-over</li>
<li>Network fail-over</li></ul></dd></dl>
<ul><li>Functional Stability</li></ul>
<dl><dd><ul><li>Accessibility</li>
<li>Conversion</li>
<li>Stability</li>
<li>Usability</li></ul></dd></dl>
<ul><li>IT Service Management (Supportability)</li>
<li>Monitoring and Alerts (to ensure proper alerts are configured in the system if something goes wrong)</li>
<li>Portability</li></ul>
<dl><dd><ul><li>Compatibility</li>
<li>Interoperability</li>
<li>Installation and Backout</li>
<li>Localization</li></ul></dd></dl>
<ul><li>Recovery (across data centres)</li></ul>
<dl><dd><ul><li>Application/system recovery</li>
<li>Data recovery</li></ul></dd></dl>
<ul><li>Reliability</li></ul>
<dl><dd><ul><li>Backup and Restoration (Recovery)</li>
<li>Disaster Recovery</li>
<li>Maintainability</li>
<li>Performance, Stress and Volume,</li>
<li>Procedures (Operability) and Supporting Documentation (Supportability)</li>
<li>Security and Penetration</li></ul></dd></dl>
<p>During OAT changes may be made to environmental parameters which the application uses to run smoothly. For example, with <a href="Microsoft_Windows" title="Microsoft Windows">Microsoft Windows</a> applications with a mixed or hybrid architecture, this may include: <a href="Windows_service" title="Windows service">Windows services</a>, <a href="Configuration_file" title="Configuration file">configuration files</a>, <a href="Web_services" class="mw-redirect" title="Web services">web services</a>, <a href="XML" title="XML">XML</a> files, <a href="COM%2B" class="mw-redirect" title="COM+">COM+</a> components, web services, <a href="Internet_Information_Services" title="Internet Information Services">IIS</a>, stored procedures in databases, etc. Typically OAT should occur after each main phase of the development life cycle: design, build, and <a href="Functional_testing" title="Functional testing">functional testing</a>. In sequential projects it is often viewed as a <i>final</i> verification before a system is released; where in agile and iterative projects, a more frequent execution of OAT occurs providing stakeholders with assurance of continued stability of the system and its operating environment.
</p><p>An approach used in OAT may follow these steps:
</p>
<ul><li>Design the system,</li>
<li>Assess the design,</li>
<li>Build the system,</li>
<li>Confirm if built to design,</li>
<li>Evaluate the system addresses business functional requirements,</li>
<li>Assess the system for compliance with non-functional requirements,</li>
<li>Deploy the system,</li>
<li>Assess operability and supportability of the system.</li></ul>
<p>For running the OAT <a href="Test_case" title="Test case">test cases</a>, the tester normally has exclusive access to the system or environment. This means that a single tester would be executing the test cases at a single point of time. For OAT the exact <b>Operational Readiness</b> quality gates are defined: both entry and exit gates. The primary emphasis of OAT should be on the operational stability, portability and reliability of the system.
</p>
<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>
<style data-mw-deduplicate="TemplateStyles:r1239543626">
/* start https://en.wikipedia.org/ */


.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}


/* end https://en.wikipedia.org/ */
</style><div class="reflist">
<div class="mw-references-wrap"><ol class="references">
<li id="cite_note-1"><span class="mw-cite-backlink"><b><a href="#cite_ref-1">^</a></b></span> <span class="reference-text"><style data-mw-deduplicate="TemplateStyles:r1238218222">
/* start https://en.wikipedia.org/ */


.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}


/* end https://en.wikipedia.org/ */
</style><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://atos.net/wp-content/uploads/2017/01/atos-operational-acceptance-testing-whitepaper.pdf">"atos-operational-acceptance-testing-whitepaper.pdf"</a> <span class="cs1-format">(PDF)</span>.</cite></span>
</li>
<li id="cite_note-2"><span class="mw-cite-backlink"><b><a href="#cite_ref-2">^</a></b></span> <span class="reference-text">ISTQB <a rel="nofollow" class="external free" href="http://istqbexamcertification.com/what-is-acceptance-testing/">http://istqbexamcertification.com/what-is-acceptance-testing/</a></span>
</li>
<li id="cite_note-ISO_29119_OAT-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-ISO_29119_OAT_3-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFAnthony_Woods2015" class="citation document cs1">Anthony Woods (2015). "Operational Acceptance - an application of the ISO 29119 Software Testing standard" (Document). Capgemini and Sogeti. pp.&nbsp;<span class="nowrap">1–</span>12.</cite></span>
</li>
<li id="cite_note-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-4">^</a></b></span> <span class="reference-text">White Paper: Operational Acceptance Testing, Business Continuity Assurance. December 2012 Dirk Dach, Dr Kai-Uwe Gawlik, Mark Mevert</span>
</li>
</ol></div></div></div><!--htdig_noindex--><div><div class="zim-footer">
This article is issued from <a class="external text" title="Last edited on 2024-10-17" href="https://en.wikipedia.org/wiki/?title=Operational_acceptance_testing&amp;oldid=1251744223">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.
</div>
</div><!--/htdig_noindex--></div>
</div>
</main>
</div>
</div>
</div>

</body></html>